Transaction id filtering for buffered programmed input/output (pio) write acknowledgements

ABSTRACT

A PIO transaction unit includes an input buffer, a response buffer, and a control unit. The input buffer may receive and store PIO write operations sent by one or more transactions sources. Each PIO write operation may include a source identifier that identifies the transaction source. The response buffer may store response operations corresponding to respective PIO write operations that are to be transmitted to the transaction source identified by the source identifier. The control unit may store a particular response operation corresponding to the given PIO write operation in the response buffer prior to the given PIO write operation being sent from the input buffer. The control unit may store the particular response operation within the response buffer if the given PIO write operation is bufferable and there is no non-bufferable PIO write operation having a same source identifier stored in the input buffer.

This application is a continuation of U.S. patent application Ser. No.12/637,338, entitled “Transaction ID Filtering for Buffered ProgrammedInput/Output (PIO) Write Acknowledgements”, filed Dec. 14, 2009.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to digital processing systems and, moreparticularly, to programmed I/O mechanisms in such systems.

2. Description of the Related Art

Programmed input/output (PIO) transactions may be used to access the I/Ospace of an I/O device or peripheral. More particularly, PIOtransactions may be used, for example, to write to configuration spaceregisters in one or more I/O devices or peripherals, or to access an I/Odevice's memory.

In many systems, although PIO transactions are necessary, there may beissues when performing PIO transactions. For example, in many cases, aprocessor may perform a PIO write and then wait for an acknowledgement.In some systems the processor may be stalled while the PIO write iscompleting and prior to an acknowledgement being received. This may beparticularly problematic when a processor is configuring a device forthe first time, or reconfiguring a device, and the processor sends aburst of PIO writes. Accordingly, PIO transaction acknowledgementlatency can be an important issue. However, trying to balance theselatencies along with transaction ordering and PIO error reporting can bedifficult in conventional systems.

SUMMARY

Various embodiments of a PIO transaction unit including transaction IDfiltering are disclosed. In one embodiment, the PIO transaction unitincludes an input buffer or queue, a response buffer, and a controlunit. The input buffer may be configured to receive and store aplurality of PIO write operations that are sent by one or moretransactions sources such as a processor or other I/O master, forexample. Each PIO write operation may include a source identifier thatidentifies the transaction source. The response buffer may be configuredto store response operations corresponding to respective PIO writeoperations that are to be transmitted to the transaction sourceidentified by the source identifier. As each PIO write operation isreceived, the control unit may be configured to determine whether agiven PIO write operation is bufferable or non-bufferable, and whetherthere are any non-bufferable write operations having the same sourceidentifier in the input buffer. If the given PIO write operation isbufferable, the control unit may be configured to store in the responsebuffer a particular response operation corresponding to the given PIOwrite operation prior to the given PIO write operation being sent to atarget of the given PIO write operation. The control unit may store theparticular response operation within the response buffer in response todetermining that the given PIO write operation is a bufferable PIO writeoperation and that there is no non-bufferable PIO write operation havinga same source identifier stored in the input buffer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one embodiment of an integrated circuitsystem including a PIO unit.

FIG. 2 is a block diagram of one embodiment of the PIO unit shown inFIG. 1.

FIG. 3 is flow diagram depicting the operation of one embodiment of thePIO unit shown in FIG. 1 and FIG. 2.

FIG. 4 is a block diagram of one embodiment of a system including theintegrated circuit system shown in FIG. 1.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to limit the invention to theparticular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention as defined by the appendedclaims. The headings used herein are for organizational purposes onlyand are not meant to be used to limit the scope of the description. Asused throughout this application, the word “may” is used in a permissivesense (i.e., meaning having the potential to), rather than the mandatorysense (i.e., meaning must). Similarly, the words “include,” “including,”and “includes” mean including, but not limited to.

Various units, circuits, or other components may be described as“configured to” perform a task or tasks. In such contexts, “configuredto” is a broad recitation of structure generally meaning “havingcircuitry that” performs the task or tasks during operation. As such,the unit/circuit/component can be configured to perform the task evenwhen the unit/circuit/component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits. Similarly, various units/circuits/componentsmay be described as performing a task or tasks, for convenience in thedescription. Such descriptions should be interpreted as including thephrase “configured to.” Reciting a unit/circuit/component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. §112, paragraph six interpretation for thatunit/circuit/component.

DETAILED DESCRIPTION

Turning now to FIG. 1, a block diagram of one embodiment of anintegrated circuit (IC) system 10 is shown. The system 10 includes asystem interface unit (SIU) 28, high performance peripherals 30, adirect memory access (DMA) unit 32, one or more other peripherals 34, aPIO unit 36, a device interface 38, a processor 40, and a memorycontroller 42.

As shown in FIG. 1, the SIU 28 is coupled to the high performanceperipherals 30, the DMA unit 32, the PIO unit 36, the processor 40, andthe memory controller 42. The DMA unit 32 is coupled to the highperformance peripherals 30, the PIO unit 36 and the other peripherals34. The PIO unit 36 is also coupled to the device interface 38. Thememory controller 42 is coupled to a memory (not shown). In oneembodiment, the IC system 10 as illustrated in FIG. 1 may be integratedonto a single integrated circuit chip as a system-on-a-chip (SOC). Inother embodiments, two or more integrated circuits may be employed toprovide the components illustrated in FIG. 1. In other embodiments, theIC system 10 may further include various other components (e.g.components coupled to the SIU 28).

The PIO unit 36 may receive and handle PIO transactions initiated by oneor more of the I/O masters that may be coupled to the SIU 28. Forexample, in one embodiment, the processor 40 may initiate PIOtransactions and the PIO unit 36 may maintain the order of PIOoperations and their responses. Further, as described in greater detailbelow, the PIO unit 36 may be configured to bypass responses for certaintypes of PIO write operations depending upon the transaction ID andwhether the transaction request is bufferable or not.

The system interface unit 28 may be a “top level” interface connectingthe various components of the system 10 and providing communicationtherebetween. The SIU 28 may include an interconnect that provides anaddress, a data, and a write response interconnect (not shown) to coupleto other components in the system 10.

The high performance peripherals 30 may include various peripherals thatare expected to generate significant bandwidth on the SIU 28, at leastas compared to the other peripherals in the system 10. For example, inone embodiment, the high performance peripherals 30 may include anetworking media access controller (MAC) such as an Ethernet MAC, awireless fidelity (WiFi) controller, and a universal serial bus (USB)controller. Other embodiments may include more or fewer peripherals, andmay categorize and/or arrange the peripherals differently. For example,the MAC and USB controller may be medium performance peripherals,whereas the WiFi controller may be a low performance peripheral. Theother peripherals 34 may include various lower bandwidth peripheralssuch as an audio subsystem, flash memory interface, general purposeinput/output (I/O), timers, an on-chip secrets memory, an encryptionengine, etc., or any combination thereof. The DMA unit may be configuredto perform transfers to and from the memory through the memorycontroller 42 on behalf of the other peripherals 34. The deviceinterface 38 may provide an interface to a number of control and statusregisters for devices such as boot memory, a power management unit,interrupt controllers, and others.

The processor 40 may implement any instruction set architecture, and maybe configured to execute instructions in that instruction setarchitecture. The processor 40 may employ any microarchitecture,including scalar, superscalar, pipelined, superpipelined, out of order,in order, speculative, non-speculative, etc., or combinations thereof.The processor 40 may include circuitry, and optionally may implementmicrocoding techniques.

The memory controller 42 may be configured to receive memory requestsfrom the system interface unit 28 (which may have received the requestsfrom one or more other components as shown in FIG. 1). The memorycontroller 42 may access memory to complete the requests (writingreceived data to the memory for a write request, or providing data fromthe memory in response to a read request). The memory controller 42 maybe configured to interface with any type of memory, such as dynamicrandom access memory (DRAM), synchronous DRAM (SDRAM), double data rate(DDR, DDR2, DDR3, etc.) SDRAM, RAMBUS DRAM (RDRAM), static RAM (SRAM),etc. The memory may be arranged as multiple banks of memory, such asdual inline memory modules (DIMMs), etc.

It is noted that other embodiments may include other combinations ofcomponents, including subsets or supersets of the components shown inFIG. 1 and/or other components. While one instance of a given componentmay be shown in FIG. 1, other embodiments may include one or moreinstances of the given component. In addition, in other variousembodiments, other components that may be coupled to the systeminterface unit 28, or portions of the other components, may also becoupled through an interface unit (not shown).

Turning now to FIG. 2, a block diagram of one embodiment of the PIO unit36 of FIG. 1 is shown. The PIO unit 36 includes a control unit 60coupled to a PIO input queue 65 and to a response queue 70. As shown,the control unit 60 includes a buffer and ID check unit 61, and an errordetect and handling unit 62.

The PIO input queue 65 includes a number of entries (as indicated by theellipsis) and is configured to receive PIO write operations fromupstream and to store each one in respective entry (e.g., entry 66)within the PIO input queue 65. The PIO input queue 65 is also configuredto send PIO write operations downstream to the DMA unit 32 and thedevice interface 38, for example. In one embodiment, the PIO input queue65 may be implemented as a first-in-first-out (FIFO) buffer. Anexemplary entry 66 is shown within the PIO input queue 65. As shown,entry 66 includes a number of fields. The first field from the left isthe bufferable/non-bufferable field, which is denoted by the ‘B’ and mayindicate whether the transaction is bufferable. In addition, entry 66includes a response field, denoted by an ‘R’, and may indicate that aresponse corresponding to the entry has already been placed in theresponse queue (i.e., bypassed). The entry 66 also includes atransaction identifier ‘ID’ field, which may be used to identify thesource of the PIO write operation. It is noted that in otherembodiments, there may be other fields that are not shown (e.g., data)for simplicity.

The response queue 70 includes a number of entries (as indicated by theellipsis) and is configured to receive, from downstream, responses tothe PIO write operations. The response queue 70 may also be configuredto send the responses upstream to the I/O master that initiated thecorresponding PIO write operation. The response queue 70 is configuredto store each response in an entry such as entry 71. In one embodiment,the response queue 65 may be implemented as a FIFO buffer. An exemplaryentry 71 is shown within the response queue 70. As shown, each responsequeue entry 71 includes a number of fields. The first field from theleft is a transaction ID field, which identifies the source of the PIOwrite operation, and which is the target of the response. The next fieldis an error field, denoted with an ‘E’, which may indicate the presenceof an error. It is noted that in other embodiments, there may be otherfields that are not shown in the illustration for simplicity.

The PIO unit 36 may control PIO transactions by responding to PIO writeoperations that are issued on the SIU 28. Accordingly, in oneembodiment, the control unit 60 may detect PIO write operations on theSIU 28. The control unit 60 may capture the address and the transactionsource ID, the bufferable bit, and any write data, and store theoperation into an entry of the PIO input queue 65. In addition, thebuffer and ID check unit 61 may determine whether the write operation isbufferable using the indication in the B field. To facilitate orderingrules among transactions with the same ID, the buffer and check unit 61may include comparison logic to determine whether any non-bufferabletransactions may be stored in the PIO input queue 65 that have the sametransaction ID as the received bufferable transaction.

In one embodiment, the control unit 60 may be configured to cause acorresponding response to be stored within an entry in the responsequeue 70 if a received operation is bufferable and there are nonon-bufferable transactions with the same ID as the received bufferableoperation stored in the PIO input queue 65, prior to the received writeoperation being sent to the target. More particularly, in oneimplementation, the control unit 60 may “bypass” the normal period ofwaiting for a response/completion acknowledgement by storing a responsethat corresponds to the received bufferable transaction within theresponse queue 70 and marking the ‘R’ field of the corresponding entryin the PIO input queue 65. Accordingly, when that response reaches thehead of the response queue 70, the response may be issued to the PIOwrite transaction source before the completion is even received from thetarget device.

However, for non-bufferable transactions, and bufferable transactionsthat have been “demoted” because there are non-bufferable operationswith the same ID already in the PIO input queue 65, responses are storedwithin the response queue 70 when they are received from the targetdevice to which the write operation was sent.

In the event that an error occurs, such as at the target device, thetarget device may notify the PIO unit 36 using one or more signals. Thecontrol unit 60 may store a corresponding response entry within theresponse queue 70 with the ‘E’ field indicating an error. Under normalconditions (i.e., a response was not already bypassed to the responsequeue 70), that response will be sent to the I/O master that issued theassociated PIO write operation when it reaches the head of the responsequeue 70. However, in one embodiment, if the response was bypassed andalready sent, the error detect and handling unit 62 may detect the errorand issue an interrupt to the I/O master that issued the associated PIOwrite operation. Although unlikely, if the response is still in theresponse queue 70, the ‘E’ field of that entry may be changed toindicate the error.

FIG. 3 is flow diagram depicting the operation of one embodiment of thePIO unit shown in FIG. 1 and FIG. 2. Referring collectively to FIG. 1through FIG. 3, and beginning in block 301 of FIG. 3, the PIO unit 36receives a PIO write operation. In one embodiment, the PIO unit 36detects the PIO write operation on the SIU 28. The buffer and ID checkunit 61 of control unit 60 inspects the operation to determine whetherthe operation is bufferable by inspecting the state of the ‘B’ field. Inone embodiment, the ‘B’ field may be a single bit, which if set,indicates the transaction is bufferable. If the write is not bufferable(block 303), the write operation is stored in the PIO input queue 65(block 331) to await its turn to be sent to the transaction target whenit reaches the head or front of the PIO input queue 65 as describedbelow in conjunction with the description of block 313.

Referring back to block 303, if the operation is bufferable (block 303),the buffer and ID check unit 61 also determines whether there are anynon-bufferable operations having the same ID as the current bufferableoperation already stored within the PIO input queue 65 by inspecting theID field of the current bufferable operation and comparing it againstthe ID field of all other operations in the PIO input queue 65 (block305).

If there are no non-bufferable operations having the same ID, thecurrent bufferable operation is stored within the PIO input queue 65(block 307) and a corresponding acknowledgement response is storedwithin the response queue 70 (block 309). The acknowledgement responsewill be sent to the I/O master that initiated the PIO write operationwhen the response reaches the head of the response queue 70, which maybe well in advance of the actual completion of the corresponding PIOwrite operation. In addition, the control unit 60 causes the ‘R’ fieldin the input queue entry of the current operation to indicate that thecorresponding response has already been stored in the response queue 70(block 311). In one embodiment, the response field ‘R’ may beimplemented as a single bit, which if set, indicates that thecorresponding response has been stored in the response queue.

As each operation in the PIO input queue 65 reaches the front or head ofthe queue, it is sent to the transaction target (e.g., DMA or deviceinterface) (block 313). If there are no errors (block 315) when thewrite operation completes, a signal that represents anacknowledgement/completion response will be sent by the target device tothe PIO unit 36. If there are no errors, the control unit 60 checks the‘R’ field of the input queue head entry, which corresponds to the writeoperation for which the acknowledgment signal was received, to determinewhether an acknowledgement response has already been placed in theresponse queue (block 317). If an acknowledgement response has alreadybeen placed in the response queue (block 319), the write operation isconsidered done and the next transaction in the PIO input queue 65 ismoved to the head, and operation proceeds as described above inconjunction with the description of block 313 and/or 301.

If a corresponding response has not already been placed in the responsequeue 70, as in the case of a non-bufferable transaction or a bufferabletransaction that was demoted due to non-bufferable transactions havingthe same ID already being in the input queue 65, then a correspondingresponse entry is placed into the response queue 70 (block 321). Thewrite operation is considered done and the acknowledgement response issent to the I/O master that initiated the PIO write when that responsereaches the head of the response queue 70. Operation proceeds asdescribed above in conjunction with the description of block 313 and/or301.

Referring back to block 315, after each write operation reaches the headof the input queue 65, the control unit 60 waits for a corresponding Acksignal. In the event of an error, either the transaction target or errordetect and handling unit 62 may provide an error signal. If an error ispresent, the error detect and handling unit 62 may check the ‘R’ fieldof the entry at the head of the PIO input queue 65 to determine whethera response entry has already been placed in the response queue 70 (block323). If an entry has not been placed in the response queue 70, acorresponding entry with an error indication is placed in the responsequeue 70 and that response is sent to the I/O master that initiated thePIO write when that response reaches the head of the response queue 70.Operation proceeds as described above in conjunction with thedescription of block 313 and/or 301.

However, if an entry has already been placed in the response queue 70(block 323), the error detect and handling unit 62 may check whether ornot the response is still in the response queue 70 (block 327). If theresponse is still in the response queue 70, the error detect andhandling unit 62 may modify the entry by changing the ‘E’ field toindicate an error has occurred (block 327). On the other hand, if thecorresponding response has already been sent to the I/O master thatinitiated the PIO write, the error detect and handling unit 62 mayinitiate an interrupt to that I/O master, thereby notifying the I/Omaster of the presence of an error (block 325). Operation proceeds asdescribed above in conjunction with the description of block 313 and/or301.

It is noted that that although the operational flow is described andshown in a particular order, it is contemplated that in otherembodiments, the operations depicted in the various blocks of FIG. 3 maybe performed in a different order, as desired.

Turning to FIG. 4, a block diagram of one embodiment of a system 400including integrated circuit system 10 is shown. The system 400 includesat least one instance of the integrated circuit system 10 of FIG. 1coupled to one or more peripherals 414 and an external memory 412. Thesystem 400 also includes a power supply 416 that may provide one or moresupply voltages to the integrated circuit 10 as well as one or moresupply voltages to the memory 412 and/or the peripherals 414. In someembodiments, more than one instance of the integrated circuit 10 may beincluded.

The external memory 412 may be any desired memory. For example, thememory may include dynamic random access memory (DRAM), static RAM(SRAM), flash memory, or combinations thereof. The DRAM may includesynchronous DRAM (SDRAM), double data rate (DDR) SDRAM, DDR2 SDRAM, DDR3SDRAM, etc.

The peripherals 414 may include any desired circuitry, depending on thetype of system 110. For example, in one embodiment, the system 400 maybe a mobile device and the peripherals 414 may include devices forvarious types of wireless communication, such as WiFi, Bluetooth,cellular, global position system, etc. The peripherals 414 may alsoinclude additional storage, including RAM storage, solid-state storage,or disk storage. The peripherals 414 may include user interface devicessuch as a display screen, including touch display screens or multi-touchdisplay screens, keyboard or other keys, microphones, speakers, etc.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

1. A programmed input/output (PIO) transaction unit comprising: an inputbuffer configured to receive and store a plurality of PIO writeoperations sent by one or more transactions sources, wherein each PIOwrite operation includes a source identifier that identifies arespective one of the one or more transaction sources; a response bufferconfigured to store response operations corresponding to respective PIOwrite operations to be transmitted to the transaction source identifiedby the source identifier; and a control unit coupled to the responsebuffer and the input buffer and configured to store in the responsebuffer a particular response operation corresponding to a given PIOwrite operation prior to the given PIO write operation being sent to atarget of the given PIO write operation in response to determining thatthe given PIO write operation is a bufferable PIO write operation andthat there is no non-bufferable PIO write operation having a same sourceidentifier stored in the input buffer.
 2. The PIO transaction unit asrecited in claim 1, wherein the control unit is further configured tostore in the response buffer, the particular response operationcorresponding to the given PIO write operation after the given PIO writeoperation is sent to the target of the given PIO write operation inresponse to determining that the given PIO write operation is anon-bufferable PIO write operation.
 3. The PIO transaction unit asrecited in claim 1, wherein the control unit is further configured tostore in the response buffer, the particular response operationcorresponding to the given PIO write operation after the given PIO writeoperation is sent to the target of the given PIO write operation inresponse to determining that there is at least one non-bufferable PIOwrite operation having a same source identifier already stored in theresponse buffer.
 4. The PIO transaction unit as recited in claim 1,wherein the control unit is configured to determine whether each PIOwrite operation is a bufferable PIO write operation based upon anindication in each PIO write operation.
 5. The PIO transaction unit asrecited in claim 1, wherein in response to detecting an occurrence of anerror associated with the given PIO write operation in which a responseoperation has already been sent to the transaction source, the controlunit is configured to initiate an interrupt to the transaction source ofthe given PIO write operation.
 6. The PIO transaction unit as recited inclaim 1, wherein the control unit is configured to cause the given PIOwrite operation to indicate that the response operation corresponding tothe given PIO write operation has been stored in the response bufferprior to the given PIO write operation being sent to the target of thegiven PIO write operation.
 7. A programmed input/output (PIO) unitcomprising: an input buffer configured to receive and store a pluralityof PIO write operations sent by one or more transactions sources,wherein each PIO write operation includes a source identifier thatidentifies a respective one of the one or more transaction sources; aresponse buffer configured to store response operations corresponding torespective PIO write operations to be transmitted to the transactionsource identified by the source identifier; and a control unit coupledto the response buffer and the input buffer and configured to store inthe response buffer a particular response operation corresponding to agiven PIO write operation after receiving an associated acknowledgementfrom a target of the given PIO write operation; wherein the control unitis configured to store the particular response operation in the responsebuffer in response to determining that the given PIO write operation isa bufferable PIO write operation and that there is at least onenon-bufferable PIO write operation having a same source identifierstored in the input buffer.
 8. The PIO transaction unit as recited inclaim 7, wherein the control unit is configured to determine whether theeach PIO write operation is a bufferable PIO write operation based uponan indicator in each PIO write operation.
 9. A method comprising:storing within an input buffer a plurality of programmed input/output(PIO) write operations received from one or more transactions sources,wherein each PIO write operation includes a source identifier thatidentifies a respective one of the one or more transaction sources;storing within a response buffer a response operation corresponding toeach respective PIO write operation to be transmitted to a source of thePIO write operation; and a control unit storing in the response buffer aresponse operation corresponding to a given PIO write operation prior tothe given PIO write operation being sent to a target of the given PIOwrite operation; the control unit storing the response operation in theresponse buffer in response to determining that the given PIO writeoperation is a bufferable PIO write operation and that there is nonon-bufferable PIO write operation having a same source identifierstored in the input buffer.
 10. The method as recited in claim 9,further comprising the control unit storing in the response buffer, theresponse operation corresponding to the given PIO write operation afterthe given PIO write operation is sent to the target of the given PIOwrite operation, in response to determining that there is at least onenon-bufferable PIO write operation having a same source identifierstored in the response buffer.
 11. The method as recited in claim 10,further comprising the control unit determine whether each PIO writeoperation is a bufferable PIO write operation based upon an indicatorwithin each PIO write operation.
 12. The method as recited in claim 15,further comprising the control unit initiating an interrupt to thetransaction source of the given PIO write operation in response todetecting an occurrence of an error associated with the given PIO writeoperation in which a response operation has already been sent to thetransaction source.
 13. The method as recited in claim 18, furthercomprising the control unit causing the given PIO write operation toindicate that the response operation corresponding to the given PIOwrite operation has been stored in the response buffer prior to thegiven PIO write operation being sent to the target of the given PIOwrite operation.
 14. A system comprising: one or more input/output (I/O)masters each configured to source programmed I/O (PIO) write operationsto one or more I/O devices; a programmed I/O (PIO) transaction unitcoupled between the I/O devices and the one or more I/O masters, whereinthe PIO transaction unit includes: an input buffer configured to receiveand store the PIO write operations, wherein each PIO write operationincludes an identifier that identifies which of the I/O masters is atransaction source of the PIO write operation, a response bufferconfigured to store a response operation corresponding to eachrespective PIO write operation to be transmitted to the transactionsource of the PIO write operation; and a control unit coupled to theresponse buffer and the input buffer, wherein the control unit isconfigured to store in the response buffer a particular responseoperation corresponding to a given PIO write operation prior to thegiven PIO write operation being sent to a target of the given PIO writeoperation in response to determining that the given PIO write operationis a bufferable PIO write operation and that there is no non-bufferablePIO write operation having a same source identifier stored in the inputbuffer.
 15. The system as recited in claim 14, wherein the control unitis further configured to store in the response buffer, the particularresponse operation corresponding to the given PIO write operation afterthe given PIO write operation is sent to the target of the given PIOwrite operation in response to determining that the given PIO writeoperation is a non-bufferable PIO write operation.
 16. The system asrecited in claim 14, wherein the control unit is further configured tostore in the response buffer, the particular response operationcorresponding to the given PIO write operation after the given PIO writeoperation is sent to the target of the given PIO write operation inresponse to determining that there is at least one non-bufferable PIOwrite operation having a same source identifier already stored in theresponse buffer.
 17. The system as recited in claim 14, wherein thecontrol unit is further configured to determine whether each PIO writeoperation is a bufferable PIO write operation based upon informationwithin each PIO write operation.
 18. The system as recited in claim 14,wherein the control unit is configured to detect errors associated withPIO write operations in which a response operation has already been sentto the transaction source, and to initiate an interrupt to thetransaction source of the PIO write operations having an error.
 19. Thesystem as recited in claim 14, wherein the control unit is configured tocause a particular field within an entry in the input buffer that storesthe given PIO write operation to indicate that the response operationcorresponding to the given PIO write operation has been stored in theresponse buffer prior to the given PIO write operation being sent to thetarget of the given PIO write operation.
 20. A system comprising: anintegrated circuit; and a memory coupled to the integrated circuit;wherein the integrated circuit includes: one or more input/output (I/O)masters each configured to source programmed I/O (PIO) write operationsto one or more I/O devices; and a programmed I/O (PIO) transaction unitcoupled between the I/O devices and the one or more I/O masters, whereinthe PIO transaction unit includes: an input buffer configured to receiveand store the PIO write operations, wherein each PIO write operationincludes an identifier that identifies which of the I/O masters is atransaction source of the PIO write operation; a response bufferconfigured to store a response operation corresponding to eachrespective PIO write operation to be transmitted to the transactionsource of the PIO write operation; and a control unit coupled to theresponse buffer and the input buffer, wherein in response to determiningthat the given PIO write operation is a bufferable PIO write operationand that there is no non-bufferable PIO write operation having a samesource identifier stored in the input buffer, the control unit isconfigured to store in the response buffer a particular responseoperation corresponding to a given PIO write operation prior to thegiven PIO write operation being sent to a target of the given PIO writeoperation.